Skip to content

Conversation

@SimplyDanny
Copy link
Contributor

Building with Bazel doesn't work at the moment. That's mainly due to the missing dependencies for SwiftRefactorTest and SwiftSyntaxMacros. However, there is also an issue with rules_python which gets fixed by the update of the Bazel version.

To alleviate the risk of causing an outdated Bazel configuration again, I also added an action that at least builds everything in PRs.

@keith
Copy link
Member

keith commented Oct 31, 2025

@swift-ci please test

@SimplyDanny

This comment was marked as off-topic.

@SimplyDanny
Copy link
Contributor Author

Could you please approve the workflow once more, @keith?

@keith
Copy link
Member

keith commented Nov 4, 2025

Started

@keith
Copy link
Member

keith commented Nov 4, 2025

@swift-ci please test

@keith
Copy link
Member

keith commented Nov 4, 2025

cc @ahoppen is it ok to add a non-blocking job for this?

@ahoppen
Copy link
Member

ahoppen commented Nov 4, 2025

I’m personally fine with running the Bazel tests in GitHub Actions (thanks for adding them) but I’d like to hear @bnbarham’s opinion as well before merging.

Copy link
Contributor

@bnbarham bnbarham left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Adding the PR test SGTM under the same guidelines as the original bazel support was added, ie. you're happy to fix any issues that come up (#1251 (review)). And having PR testing should only help with that I imagine :)

@bnbarham
Copy link
Contributor

@swift-ci please test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants